Payment Methods Biz API

(0 reviews)

DELETE - paymentMethod (Digital to SF)

DELETE

This operation allows to delete a payment method from SF

Request

This section defines all the possible data structures sent by the client when consuming the method.

URL PARAMS

nametypedescriptionrequired
businessIdstring2 letter ISO 3166 country code ( PR ) identifying the business unit.
Expected one is "PR"-Puerto Rico
Y
idstringPaymentMethod idY

Security Headers

nametypedescriptionrequired
client_idstringThe client_id identifying the channel. Minimum characters: 5Y
client_secretstringPassword associated with the client_id. Minimum characters: 5Y
nametypedescriptionrequired
X-Correlation-IDstringIdentifier that correlates HTTP request between a client and server. Any identification model (UUDI, checksum, etc.) can be used, as long as it is a unique value to differentiate a transaction.N

Body

Request Body for PR

{
    "account": [
        {
            "id": "BANXXXX-CANYYY",
            "@type": "BillingAccount",
            "relatedParty": [
                {
                    "id": "649824098",
                    "@type": "msisdn"
                }
            ]
        }
    ],
    "relatedParty": [
        {
            "name": "Digital",
            "@type": "channel"
        }
    ]
}

Definitions

Each of the request parameters is detailed.

nametypedescriptionrequiredpossible values
accountarrayY
account.idstringValue of Billing Account Number Conditional mandatory. either Billing Account Number or MSISDN should be passedY*BANXXXX-CANYYY
account.@typestringtype of account.here it is Billing AccountNBillingAccount
account.relatedPartyarrayY*
account.relatedParty.idstringValue of MSISDN Conditional mandatory. either Billing Account Number or MSISDN should be passedY*649824098
account.relatedParty.@typestringtype is MSISDNNmsisdn
relatedPartyarrayY
relatedParty.namestringName of the relatedPartyYDigital/ivr
relatedParty.@typestringThe type of the relatedPartyYchannel

Response

In this section all the possible data structures received by the client at the moment of responding the method are defined.

Possible response success

This section defines all the possible data structures received by the client and that must be considered satisfactory at the time of responding to the method.

[ 204 ] No content

Reviews